美国专利US20010008023A1 Program-interface converter for multiple-platform computer systems

专利PDF首页>>美国专利

专利附录

专利说明

权利要求

类似技术

同族专利

引用文献

法律状态

优先权

专利摘要:
A utility program for software development generates a synchronized set of translation modules for application program interfaces in a emulated platform. The utility builds the translation modules from iterated function templates having generalized function code, exception templates with special-purpose code, and types templates for converting data types from the emulated platform.
公开号:US20010008023A1
申请号:US09/791,006
申请日:2001-02-22
公开日:2001-07-12
发明作者:Barry Bond；Ori Gershony；David Hastings；Jonathan Lew；Alan Warwick
申请人:Microsoft Corp；
IPC主号:G06F8-30

专利说明:
[0001] The present invention relates to electronic data processing, and more specifically concerns a software tool for generating a set of translation-code modules for translating application-program interfaces (APIs) from one platform to another, for use with an emulator which allows application programs written for one platform to be executed on a different platform. [0001] BACKGROUND OF THE INVENTION
[0002] Present-day application programs almost never interface directly to the hardware of the computer system in which they execute. Instead, application program interfaces (APIs) call code modules which control the hardware, or which call programmed interfaces at yet lower levels. Most API code modules reside in an operating system (OS), although others may exist in a basic input/output system (BIOS), or in other places. Code modules for API functions typically reside in freestanding dynamic link library (DLL) files each containing routines for carrying out dozens or even hundreds of API functions. [0002]
[0003] Executing an application program written for one computer processor, operating system, or other platform on another platform requires a program, variously known as an emulator, simulator, interpreter, or translator, to convert instructions, data formats, application-program interfaces (APIs), and other characteristics of the application from the those of its original platform to those of the native platform in which the emulator runs. Sometimes the original platform has been replaced, but the old application must still be run on the new platform. Sometimes programs are written to an abstract platform, so that the same application can be executed on numerous different platforms merely by writing an emulator for each native platform that is to host the abstract platform. [0003]
[0004] An emulator subsystem generally has two major components. The emulator itself converts the original processor instructions from the application into instructions or groups of instructions appropriate to the processor of the new platform, and executes them. An API translation layer “thunks” API calls from the original platform being emulated into calls to APIs written for the native platform; that is, it intercepts API calls made by an application written for the emulated platform, converts their arguments from the calling convention of the original platform to that of the native platform, then calls an appropriate native-platform module for executing the API function. A translation module or “API thunk” is a piece of program code in the translation layer which executes between a particular original API and the operating system running on the native platform. [0004]
[0005] Conventional practice involves hand-writing thunk code for each new and modified API. However, an API set may change daily during the development of an operating system. Also, the number of APIs can be very large. The Microsoft Windows NT operating system, for example, contains more than 3,500 APIs in 42 different DLL modules. Therefore, manual production of individual API translation code becomes increasingly impractical. Increasingly shorter product cycles compounds this problem. [0005]
[0006] Some interface modules or thunks have been generated from hand-written descriptors for each separate API. However these must be maintained separately from the APIs themselves, and thus involve costly additional effort. They also suffer from “synchronization” problems: if one or more modules inadvertently escape an update between one development iteration and the next, their down-level code may mistranslate an API, or may crash the system. Such problems can be difficult to find, thus forcing the entire development effort to wait. [0006]
[0007] Alternatively, a software tool has been employed to create a set of skeleton API thunks as C-language source files which were then hand-modified. This approach is impractical, in that rerunning the tool destroys all the hand edits. [0007] SUMMARY OF THE INVENTION
[0008] A utility program according to the present invention creates and automatically updates code modules for translating APIs written for one platform so that they will execute properly on a different platform. The utility, executed for every new development iteration of an operating system or other software environment, uses a set of templates for constructing source code for the translation modules, based upon the functions performed by the APIs. Special translation requirements are handled by exception templates containing personalized translation code. Another kind of template performs type conversions from the original APIs= parameters or arguments into those of the different platform. [0008]
[0009] Automatic code generation in this manner enables much faster development iterations by providing an automated method of synchronizing the translation modules with changes made to the new operating system or environment. The code generator ensures that all translation modules are at the current updated level, which prevents system crashes caused by incompatible modules. It also greatly reduces errors within individual code modules resulting from prior hand generation methods, and eliminates errors across modules caused from different people working independently on different modules. [0009]
[0010] Other features and advantages, as well as modifications and additions within the scope of the invention, will appear to those skilled in the art from the following description. [0010] DESCRIPTION OF THE DRAWINGS
[0011] FIG. 1 is a block diagram of a computer system in which the invention may be practiced. [0011]
[0012] FIG. 2 is a high-level block diagram of a multiple-platform emulation environment in which the invention finds utility. [0012]
[0013] FIG. 3 is a high-level block diagram of a translator utility according to the invention, along with its inputs and outputs. [0013]
[0014] FIG. 4 is a flow diagram showing the operation of the translator of FIG. 3. [0014] DETAILED DESCRIPTION
[0015] FIG. 1 provides a brief, general description of a suitable computing environment in which the invention may be implemented. Hardware and software environments will first be discussed, followed by a detailed description of the invention comprising a tool for creating and automatically updating code modules for translating APIs written for one platform so that they will execute properly on a different platform. The invention will hereinafter be described in the general context of computer-executable instructions such as program modules, executed by a personal computer (PC); however, other environments are possible. Program modules include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types. Those skilled in the art will appreciate that the invention may be practiced with other computer-system configurations, including hand-held devices, multiprocessor systems, microprocessor-based programmable consumer electronics, network PCs, minicomputers, mainframe computers, and the like. The invention may also be practiced in distributed computing environments where tasks are performed by remote processing devices linked through a communications network. In a distributed computing environment, program modules may be located in both local and remote memory storage devices. [0015]
[0016] FIG. 1 shows an exemplary system for implementing the invention. It employs a general-purpose computing device in the form of a conventional personal computer [0016] 20, which includes processing unit 21, system memory 22, and system bus 23 that couples the system memory and other system components to processing unit 21. System bus 23 may be any of several types, including a memory bus or memory controller, a peripheral bus, and a local bus, and may use any of a variety of bus structures. System memory 22 includes read-only memory (ROM) 24 and random-access memory (RAM) 25. A basic input/output system (BIOS) 26, stored in ROM 24, contains the basic routines that transfer information between components of personal computer 20. BIOS 24 also contains start-up routines for the system. Personal computer 20 further includes hard disk drive 27 for reading from and writing to a hard disk (not shown), magnetic disk drive 28 for reading from and writing to a removable magnetic disk 29, and optical disk drive 30 for reading from and writing to a removable optical disk 31 such as a CD-ROM or other optical medium. Hard disk drive 27, magnetic disk drive 28, and optical disk drive 30 are connected to system bus 23 by a hard-disk drive interface 32, a magnetic-disk drive interface 33, and an optical-drive interface 34, respectively. The drives and their associated computer-readable media provide nonvolatile storage of computer-readable instructions, data structures, program modules and other data for personal computer 20. Although the exemplary environment described herein employs a hard disk, a removable magnetic disk 29 and a removable optical disk 31, those skilled in the art will appreciate that other types of computer-readable media which can store data accessible by a computer may also be used in the exemplary operating environment. Such media may include magnetic cassettes, flash-memory cards, digital versatile disks, Bernoulli cartridges, RAMs, ROMs, and the like.
[0017] Program modules may be stored on the hard disk, magnetic disk [0017] 29, optical disk 31, ROM 24 and RAM 25. Program modules may include operating system 35, one or more application programs 36, other program modules 37, and program data 38. A user may enter commands and information into personal computer 20 through input devices such as a keyboard 40 and a pointing device 42. Other input devices (not shown) may include a microphone, joystick, game pad, satellite dish, scanner, or the like. These and other input devices are often connected to the processing unit 21 through a serial-port interface 46 coupled to system bus 23; but they may be connected through other interfaces not shown in FIG. 1, such as a parallel port, a game port, or a universal serial bus (USB). A monitor 47 or other display device also connects to system bus 23 via an interface such as a video adapter 48. In addition to the monitor, personal computers typically include other peripheral output devices (not shown) such as speakers and printers.
[0018] Personal computer [0018] 20 may operate in a networked environment using logical connections to one or more remote computers such as remote computer 49. Remote computer 49 may be another personal computer, a server, a router, a network PC, a peer device, or other common network node. It typically includes many or all of the components described above in connection with personal computer 20; however, only a storage device 50 is illustrated in FIG. 1. The logical connections depicted in FIG. 1 include local-area network (LAN) 51 and a wide-area network (WAN) 52. Such networking environments are commonplace in offices, enterprise-wide computer networks, intranets and the Internet.
[0019] When placed in a LAN networking environment, PC [0019] 20 connects to local network 51 through a network interface or adapter 53. When used in a WAN networking environment such as the Internet, PC 20 typically includes modem 54 or other means for establishing communications over network 52. Modem 54 may be internal or external to PC 20, and connects to system bus 23 via serial-port interface 46. In a networked environment, program modules depicted as residing within 20 or portions thereof may be stored in remote storage device 50. Of course, the network connections shown are illustrative, and other means of establishing a communications link between the computers may be substituted.
[0020] FIG. 2 shows a software environment [0020] 200 for running an application program 210 for one platform on a processor 220 representing a different platform. The elements enclosed in dashed line 201 are elements designed to be executed on a first platform such as a processor 21, FIG. 1, of the Intel AX86≅ familyXfor example an Intel 80386, 80486, or Pentium microprocessor. The other elements execute on a second platform, such as a Digital Equipment Corp. AAlpha≅ or an IBM APowerPC≅ microprocessor serving as processor 21. This description refers to the first and second platforms as the AX86≅ and Anative≅ platforms, respectively. For purposes of illustration, a native-platform version 230 of the Microsoft NT operating system serves as OS 35, FIG. 1.
[0021] Conventional emulator program [0021] 240 translates the instructions, data, and interfaces (APIs) of an X86-platform application program such as 36, FIGS. 1 and 2, from those of the X86 platforms to equivalent operations in the native platform. The APIs of an application program are actually calls to a set 250 of API modules 251-253, only a very few of which are shown in FIG. 2. API modules are commonly grouped into dynamic link libraries such as 254. As noted previously, OS 230 has thousands of APIs in more than forty DLLs; this set, collectively known as AWin32,≅ is recompiled into a new Abuild≅ almost daily during a development effort. When application 210 calls an API written for the X86 platform, such as API 251, a conventional API translation layer 241 in emulator 240 retrieves the proper API module 251, and calls an associated translation-code module, or Athunk,≅ 261 to convert any API arguments and data to the correct format for the native platform, and to perform functions which emulate those the API would have performed on the original X86 platform. The set of thunks 260 includes a separate module 261-262 for each X86 API 251-252. APIs such as 253 written for the native platform execute directly when called from OS 230, and do not require thunks.
[0022] FIG. 3 is a high-level block diagram [0022] 300 showing a translator utility according to the invention, along with its inputs and outputs. Some of the elements shown in FIG. 2 have different labels in FIG. 3, to denote that the corresponding elements are in compiled object-code form in FIG. 2, but exist as source-code files in FIG. 3.
[0023] In its source-code form, each DLL [0023] 254, FIG. 2, is a collection 310 of files 311 each containing instructions in a language such as C for an API 250, FIG. 2. Each file represents one or more functions 312 to be performed by one of the APIs 251-252. [@@ Inventor note 1] (Some terminology: a dynamic link library is generated from three source files, viz a C source-code file, a C header file, and a .DEF file. The compiler converts these into two object files, a .DLL code file and an import .LIB file.)
[0024] A module-definition file (.DEF) file [0024] 322 specifies the list of functions which are to be exported from DLL 320 as APIs. The .DEF file compiled into an import library (.LIB) file 321. The .LIB file is significant because the API name exported from the DLL may differ from the function name in source file 311; for example, an entry FOO=BAR@4 in a .DEF file instructs the linker to export the function known internally as FOO from the DLL as BAR. Thunk generator 330 uses .LIB file 321 to associate an internal function name with an exported API name. C-language files have associated header (.H) files 313 that specify the external interface of their code file 311, such as data types and external variable names. In particular, header files include type information 315 for functions 312 in code files 311.
[0025] For example, a .H header file could contain a type definition such as: [0025]
[0026] Typedef struct tagFoo {[0026]
[0027] int member1; [0027]
[0028] int member2; [0028]
[0029] } *PFOO [0029]
[0030] and a function declaration: [0030]
[0031] int AnApi {PFOO arg1, char *}; [0031]
[0032] Generator [0032] 330 stores this information for all APIs. The entries for the above example might be:
[0033] TYPENAME struct tagFoo [0033]
[0034] MEMBER LIST [0034]
[0035] MEMBER NAME member1 [0035]
[0036] MEMBER TYPE int [0036]
[0037] MEMBER OFFSET 0 [0037]
[0038] MEMBER NAME member2 [0038]
[0039] MEMBER TYPE int [0039]
[0040] MEMBER OFFSET 4 [0040]
[0041] TYPENAME PFOO [0041]
[0042] INDIRECTION 1 [0042]
[0043] BASETYPE struct tagFoo [0043]
[0044] APINAME AnApi [0044]
[0045] RETURN TYPE int [0045]
[0046] ARG NAME arg1 [0046]
[0047] ARG TYPE PFOO [0047]
[0048] ARG NAME <noname> [0048]
[0049] ARG TYPE char * [0049]
[0050] Finally, a conventional definitions (.DEF) file [0050] 322 may instruct a conventional linker (not shown) in OS 230 to export an internal API name from DLL 320 as a different name.
[0051] Translation generator [0051] 330 uses information from files 311, 313, and 321 to build C-language source-code files 340 which can be compiled into the translation-code modules 260 in FIG. 2. The invention provides a novel set of template files 350 for this purpose. Template (.TPL) files are descriptions of how to generate translation-code modules (Athunks≅). They comprise small amounts of hand-generated C code which implement generalized forms for iterating over API functions and their arguments, and for handling special cases which may arise in particular APIs. Each template has the following syntax:
[0052] [Type_of_Template] [0052]
[0053] TemplateName=Name_Of_Template [0053]
[0054] CGenBegin= [0054]
[0055] <code to generate when this template is expanded> [0055]
[0056] CGenEnd= [0056]
[0057] There are four types of template [0057] 350.
[0058] The iterated-function (IFunc) template [0058] 351 iterates over API functions. Generator 330 expands one of these for each exported function in an API. The IFunc template 351 is the default expansion for APIs. The following example template will generate a skeleton thunk 340.
[0059] [IFunc][0059]
[0060] TemplateName=HostFuncs [0060]
[0061] CGenBegin= [0061]
[0062] void [0062]
[0063] wh@ApiName (PULONG BaseArgs, ULONG RetVal) [0063]
[0064] {[0064]
[0065] @ApiFnRet *pRetVal=(@ApiFnRet *) RetVal; [0065]
[0066] @Types (Locals) [0066]
[0067] @Types (Body) [0067]
[0068] @IfApiRet (*pRetVal=) @ApiName (@IfArgs (@ArgList (*((@ArgType [0068]
[0069] *) [0069]
[0070] (@ArgAddr (BaseArgs))) @ArgMore(,)))); [0070]
[0071] @Types (Return) [0071]
[0072] } [0072]
[0073] CGenEnd= [0073]
[0074] Generator [0074] 330 expands each of the >@=-prefixed keywords in template 351 from the data collected from files 313 and 321 for a particular API 310 as follows:
[0075] @ApiName Internal name of the API [0075]
[0076] @ApiFnRet Return type of the API [0076]
[0077] @Types(x) Expands Type templates of the form >x= [0077]
[0078] @IfApiRet(x) Expands >x= if the return type of the API is non-void [0078]
[0079] @If Args(x) Expands >x= if the API has arguments [0079]
[0080] @ArgList(x) Iterates over all arguments, expanding >x= for each argument [0080]
[0081] @ArgType Type of argument [0081]
[0082] @ArgAddr(x) Address of the argument, relative to >x= [0082]
[0083] @ArgMore(x) Expands if there are more arguments after the current one [0083]
[0084] For example, an API with prototype >HWND FindWindowA(LPSTR lpClass, LPSTR lpWindow)= expands to: [0084]
[0085] whFindWindowA (PULONG pBaseArgs, ULONG RetVal) [0085]
[0086] {[0086]
[0087] HWND *pRetVal= (HWND *) RetVal; [0087]
[0088] *pRetVal=FindWindowA(*(LPSTR *) (pBaseArgs+0), * (LPSTR *) [0088]
[0089] (pBaseArgs+1)); [0089]
[0090] } [0090]
[0091] An exception-function (EFunc) template [0091] 352 recognizes a particular API name, and overrides the default IFunc template 351 for that API. The following example template 352 produces fixed code for the particular API named >SetErrorMode=.
[0092] [EFunc][0092]
[0093] TemplateName=SetErrorMode [0093]
[0094] CGenBegin= [0094]
[0095] void [0095]
[0096] wh@ApiName (PULONG BaseArgs, ULONG RetVal) [0096]
[0097] {[0097]
[0098] @ApiFnRet *pRetVal= (@ApiFnRet *) RetVal; [0098]
[0099] *pRetVal=SetErrorMode ((*(UINT *) pBaseArgs) * [0099]
[0100] SEM_NOALIGNMENTFAULTEXCEPT) [0100]
[0101] *pRetVal &= -SEM_NOALIGNMENTFAULTEXCEPT; [0101]
[0102] } [0102]
[0103] CGenEnd= [0103]
[0104] EFunc templates provides a facility for custom-writing code for an API, while preserving robustness against API changes. Of course, the code for such an API can always be rewritten merely by rewriting its EFunc template. [0104]
[0105] A types (Types) template [0105] 353 creates a thunk 340 for each parameter, or argument, of each API file 311 which matches a specified type name. Types templates are powerful in that generator 330 applies them automatically to new APIs, providing correct thunking without manual intervention. Consider the following examples:
[0106] [Types] [0106]
[0107] TemplateName=Locals [0107]
[0108] TypeName=LPSTR [0108]
[0109] IndLevel=0 [0109]
[0110] CGenBegin= [0110]
[0111] @ArgLocal= * ((@ArgType *) (pBaseArgs+ @ArgOff)); [0111]
[0112] CGenEnd= [0112]
[0113] [Types] [0113]
[0114] TemplateName=Body [0114]
[0115] TypeName=LPSTR [0115]
[0116] IndLevel=0 [0116]
[0117] CGenBegin= [0117]
[0118] VALIDATE_LPSTR (@ArgNameLocal); [0118]
[0119] CGenEnd= [0119]
[0120] With these two templates, any API [0120] 311 which takes the C-language LPSTR data type automatically receives the special-purpose Types code in addition to the IFunc code for the default IFunc template. For example, the >FindWindowA= API described above now expands to:
[0121] {[0121]
[0122] HWND *pRetVal= (HWND *) RetVal; [0122]
[0123] LPSTR lpclass= *((LPSTR *) (pBaseArgs+0); [0123]
[0124] LPSTR lpWindow= *((LPSTR *) (pBaseArgs+1); [0124]
[0125] VALIDATE_LPSTR (lpClass); [0125]
[0126] VALIDATE_LPSTR (lpWindow); [0126]
[0127] *pRetVal= FindWindowA (lpClass, lpwindow); [0127]
[0128] }[0128]
[0129] A code template [0129] 354 operates like a macro. It contains code which may be common to a number of other templates, and is referred to by name in those templates. For example, if the line
[0130] *pRetVal= SetErrorMode ((*(UINT *) pBaseArgs)* [0130]
[0131] occurs many times in many different template s [0131] 351, 352, or 353, then that line could be placed in a code template such as one named, Aserrm.= The referring templates, such as the example above, then merely replace that line with the name of the macro, for example A[@serrm]≅. The conventional C macro facility then replaces the name with the code; C macros can, of course, be much more complex than this simple example.
[0132] Although the above templates are shown as written in the C language, they are language-independent. Templates [0132] 350 may generate code in C++, in assembler language, or in any other desired form.
[0133] FIG. 4 describes the steps [0133] 400 carried out by translation-code generator 330, FIG. 3. The generator is run at 401 for every build of the operating system 230 or other entity whose APIs require regeneration. At its conclusion 402, the entire set of API translation-module source-code files 340 has been synchronized at the same level, and can be compiled in a conventional manner into the set of object-code modules 260, FIG. 2 which together form an API-translation portion (the Athunk layer≅) of emulator 240.
[0134] Block [0134] 410 scans all the DLLs 254 belonging to the OS 230 to identify the set of APIs (261, 262, . . . in FIG. 2) which require regeneration. The names of these APIs are in the export table 314 and in the import .LIB file 321 of each DLL, as previously described. (As a technical aside, the raw exports come from the import .LIB. However, many of them may be unnamed ordinals or renamed C functions. In order to obtain type information, generator 330 must reconstruct the name of the original function that implements each API. Thus, it must sometimes unmap the export name back to the function name.) Step 403 then sequentially selects a current API in the set for processing.
[0135] Step [0135] 420 may identify the current API as having an exception template 352, by a conventional table-lookup in a list of the exception-template names. If such a template exists, step 421 accesses the associated EFunc template, and step 422 places its source code into a thunk file 340 for that API.
[0136] If the current API is a normal API, step [0136] 430 reads export table 314 of its header file 313 to extract the names of all its exported functions. Step expands the IFunc template 351 for those functions, as described above. When step 431 has iterated through all the exported functions of the current API, exit 432 progresses to the next step.
[0137] Step [0137] 440 cycles through the parameters (arguments) of the current API, sequentially selecting one as a current parameter. If step 441 determines that a Types template 353 exists for this parameter type, then step 442 places the template=s source code in the module 340, so that the API will process that argument type correctly. Most types templates substitute a different value for a parameter. However, a types template may perform other functions, such as validating the range of a parameter. Control passes to exit 443 when all Types templates have been processed.
[0138] Step [0138] 450 processes Code templates 354, FIG. 3. Whenever the name of a code template appears (as a macro name) in template-processing step 422, 432, or 442, dashed lines 451 call step 450 to expand a particular named code template and return the code to the calling template. Step 450 may actually occur later, when the thunk source-code files 340 are conventionally compiled into object-code modules 260.
[0139] It is to be understood that the above description is intended to be illustrative, and not restrictive. The invention may be used to provide for execution of interfaces from multiple prior platforms as opposed to just one. Further, template matching can be done in many different manners, such as by having a field in an interface which directly identifies a desired template. Many other embodiments will be apparent to those skilled in the art upon reviewing the above description. The scope of the invention should, therefore, be determined with reference to the appended claims, along with the full scope of equivalents to which such claims are entitled. [0139]

权利要求:
Claims (21)
[1" id="US-20010008023-A1-CLM-00001] 1. In a programmable digital computer, a method for generating a synchronized set of translation modules containing program code for executing on a native platform a corresponding set of interface modules written for an emulated platform, the method comprising:
identifying the set of interface modules written for the emulated platform and requiring translation for the second platform;
for all interface modules in the set, sequentially selecting a source-code file representing one of the set of interface modules as a current module;
extracting from the current module data representing a group of functions exported by the current module;
matching the current-module data to a group of function templates, at least some of the templates containing generalized program code written for the native platform and performing functions from the emulated platform;
selecting at least one of the templates in response to the matching step; and
for each template selected, converting the generalized program source code in the template into personalized program code constituting at least part of the translation module for the current module.
[2" id="US-20010008023-A1-CLM-00002] 2. A method according to
claim 1 , further comprising:
determining that the current module matches one of a group of exception templates each containing program code; and
generating at least part of the translation module for the current module from the program code of the one exception template.
[3" id="US-20010008023-A1-CLM-00003] 3. A method according to
claim 2 , further comprising:
bypassing matching the current-module data against the function templates when the current module matches one of the group of exception templates.
[4" id="US-20010008023-A1-CLM-00004] 4. A method according to
claim 1 wherein the current module has at least one parameter having one of a group of types, further comprising
matching the one parameter to one of a group of types templates; and
generating at least some of the program code of the current translation module from the one types template.
[5" id="US-20010008023-A1-CLM-00005] 5. A method according to
claim 1 , further comprising:
determining that one of the templates specifies the name of one of a group of a code templates; and
incorporating source code from the specified code template in the one template whenever the one template provides code for a translation module.
[6" id="US-20010008023-A1-CLM-00006] 6. A method according to
claim 1 wherein the interface modules have an import table and reside in at least one link library, and wherein the identifying step comprises:
scanning the link library; and
reading the names of the interface modules in the set from the import tables.
[7" id="US-20010008023-A1-CLM-00007] 7. A method according to
claim 1 , further comprising:
iterating the matching, selecting and converting steps over each of the functions in the group of functions.
[8" id="US-20010008023-A1-CLM-00008] 8. A computer system for producing a set of synchronized translation modules each containing code for translating a different interface written for a first platform into instructions for executing that interface on a second platform, the system comprising:
a set of interface files each comprising source code for implementing one of the interfaces;
a set of header files associated with respective ones of the interface files and containing the names of functions exported by the respective interface files;
an import library containing names of the interface files in the set;
a group of function template files containing generalized source code for executing a group of translation functions; and
a generator for matching certain of the interface modules to at least one of the function templates and for converting the generalized code of the one function template into personalized source code for executing at least one of those functions exported by the interface modules, the personalized code forming at least a portion of the translation modules.
[9" id="US-20010008023-A1-CLM-00009] 9. A computer system according to
claim 8 , further comprising a group of exception template files associated with certain ones of the translation modules, and wherein the generator produces source code forming at least part of the code of the translation modules from one of the exception templates instead of from the function templates.
[10" id="US-20010008023-A1-CLM-00010] 10. A computer system according to
claim 8 , further comprising a group of types templates respectively containing source code for a group of data types found in certain of the interface modules, and wherein the generator incorporates forming a part of the translation modules from those of the types templates corresponding to the data types found in the certain interface modules.
[11" id="US-20010008023-A1-CLM-00011] 11. A digital computer system for executing an application program written for an emulated platform on a native platform, comprising:
an operating system executing on the native platform;
a set of interface modules executable on the emulated platform;
an emulator for executing on the native platform an application program written for an emulated platform and having a set of interfaces executable on the emulated platform;
a group of function templates each containing generalized code for executing a function;
a group of types templates each containing conversion code for converting a data type of the emulated platform to a data type of the native platform; and
a set of translation modules for executing respective ones of the interface modules on the native platforms, the translation modules containing personalized code from the function templates and conversion code from the types templates.
[12" id="US-20010008023-A1-CLM-00012] 12. A digital computer system according to
claim 11 , further comprising a group of exception templates containing code associated with particular respective ones of the interface modules, wherein at least some of the translation modules contain code directly contained in the exception modules.
[13" id="US-20010008023-A1-CLM-00013] 13. A computer-readable medium having computer-executable instructions for generating a synchronized set of translation modules containing program code for executing on a native platform a corresponding set of interface modules written for an emulated platform by performing the steps of:
identifying the set of interface modules written for the emulated platform and requiring translation for the native platform;
for all interface modules in the set, sequentially selecting a source-code file representing one of the set of interface modules as a current module;
extracting from the current module data representing a group of functions exported by the current module;
matching the current-module data to a group of function templates, at least some of the templates containing generalized program code written for the native platform and performing functions from the emulated platform;
selecting at least one of the templates in response to the matching step; and
for each template selected, converting the generalized program source code in the template into personalized program code constituting at least part of the translation module for the current module.
[14" id="US-20010008023-A1-CLM-00014] 14. A medium according to
claim 13 , including further instructions for:
determining that the current module matches one of a group of exception templates each containing program code; and
generating at least part of the translation module for the current module from the program code of the one exception template.
[15" id="US-20010008023-A1-CLM-00015] 15. A medium according to
claim 13 wherein the current module has at least one parameter having one of a group of types, the medium including further instructions for:
matching the one parameter to one of a group of types templates; and
generating at least some of the program code of the current translation module from the one types template.
[16" id="US-20010008023-A1-CLM-00016] 16. A method for automatically generating translation code for executing interfaces written for a first platform on a second, different platform, comprising:
constructing a generalized template capable of performing a plurality of different functions;
extracting a plurality of functions performed by the interfaces written for the first platform; and
personalizing the generalized template to produce translation code for each of the functions performed by the interfaces.
[17" id="US-20010008023-A1-CLM-00017] 17. A method according to
claim 16 , further comprising:
constructing a plurality of additional templates each associated with a particular type of parameter in the interfaces; and
generating translation code from one of the additional templates for the parameters associated with any of the additional templates.
[18" id="US-20010008023-A1-CLM-00018] 18. A method for automatically generating translation code for executing an interface written for a first platform on a second, different platform, comprising:
selecting one of a plurality of generalized templates based on information contained in an interface written for the first platform; and
personalizing the generalized template to produce translation code for the interface to execute on the second platform.
[19" id="US-20010008023-A1-CLM-00019] 19. The method of
claim 18 and further comprising the step of repeating the selecting and personalizing steps for each interface written for the first platform until all interfaces in a program are translated.
[20" id="US-20010008023-A1-CLM-00020] 20. The method of
claim 18 , wherein the information comprises functions performed by the interface.
[21" id="US-20010008023-A1-CLM-00021] 21. A computer-readable medium having computer-executable instructions for generating a synchronized set of translation modules for executing an interface written for a first platform on a second, different platform, by causing a suitably configured computer system to perform the steps of:
selecting one of a plurality of generalized templates based on information contained in an interface written for the first platform; and
personalizing the generalized template to produce translation code for the interface to execute on the second platform.

类似技术:

公开号 | 公开日 | 专利标题

US6810517B2|2004-10-26|Program-interface converter for multiple-platform computer systems

JP3041222B2|2000-05-15|Source code creation system and method

US6298481B1|2001-10-02|System for modifying the functionality of compiled computer code at run-time

US6557100B1|2003-04-29|Fastpath redeployment of EJBs

US5675805A|1997-10-07|Programming system for generating client and server programs from an undistributed application program

US7162709B2|2007-01-09|System and method for common code generation

US5675801A|1997-10-07|Object oriented system and method for generating target language code

US6342905B1|2002-01-29|Object oriented apparatus and method for providing a graphical user interface for host-based software applications

US6141792A|2000-10-31|Object oriented framework for specifying the format of compiler output with a template facility

US7346897B2|2008-03-18|System for translating programming languages

EP0420461A2|1991-04-03|Portable and dynamic distributed applications architecture

US20020013862A1|2002-01-31|Method for data access code generation

US5881289A|1999-03-09|Remote compiling of source code for cross development

KR20010050408A|2001-06-15|Version-Adaptive Serialization and Deserialization of Program Objects

JP2001109628A|2001-04-20|Software system and its developing method

US20030226134A1|2003-12-04|Representation of core files in a generic format

JPH1083293A|1998-03-31|Error correction compiler

US20050177818A1|2005-08-11|Integration of external tools into an existing design environment

US20030145127A1|2003-07-31|Method and computer program product for providing a device driver

JPH08512153A|1996-12-17|Dynamic browser system

EP0706125A1|1996-04-10|Object oriented system and method for generating target language code

KR960013965B1|1996-10-10|Auto-generation of menu of mobile station management system

Baker et al.1997|Ada bindings for C interfaces: Lessons learned from the florist implementation

Anderson1989|An Introductory User’s Guide to IRAF Scripts

Packard’s SoftBench1994|Object-oriented software-development tools

同族专利:

公开号 | 公开日

JP3641430B2|2005-04-20|

US6233731B1|2001-05-15|

EP1021762A1|2000-07-26|

WO1999009474A1|1999-02-25|

AT252743T|2003-11-15|

DE69819188D1|2003-11-27|

US6026238A|2000-02-15|

DE69819188T2|2004-05-19|

JP4128995B2|2008-07-30|

JP2005100437A|2005-04-14|

EP1021762B1|2003-10-22|

JP2001516079A|2001-09-25|

US6810517B2|2004-10-26|

引用文献:

公开号 | 申请日 | 公开日 | 申请人 | 专利标题

US6233731B1|1997-08-18|2001-05-15|Microsoft Corporation|Program-interface converter for multiple-platform computer systems|US20040181785A1|2003-03-13|2004-09-16|Zwirner Eric W.|Extreme pipeline and optimized reordering technology|

US20040225671A1|2003-05-08|2004-11-11|I2 Technologies Us, Inc.|Data integration system with programmatic source and target interfaces|

EP1526455A2|2003-10-24|2005-04-27|Hewlett-Packard Development Company, L.P.|Interface module|

US20050251583A1|2004-04-26|2005-11-10|Rothman Michael A|System and method to conditionally shrink an executable module|

US20060005163A1|2004-06-30|2006-01-05|Jens Huesken|Reusable component in a collaboration workspace|

US20070169010A1|2005-10-31|2007-07-19|Dhi Technologies, Inc.|Multiplatform programming environment|

US20070234147A1|2006-01-11|2007-10-04|Tsuyoshi Nakamura|Circuit analysis device|

US20080028384A1|2006-07-21|2008-01-31|Karlheinz Dorn|Interconnection interface for flexible online/offline deployment of an n-layered software application|

US7337438B1|2003-03-31|2008-02-26|Applied Micro Circuits Corporation|Macros to support structures for an assembler that does not support structures|

US20080256564A1|2007-04-10|2008-10-16|Microsoft Corporation|Application Compatibility Using a Hybrid Environment|

US8776031B1|2012-08-09|2014-07-08|Noble Systems Corporation|Manipulating resources embedded in a dynamic-link library|JPS6195449A|1984-10-17|1986-05-14|Nec Corp|Source program control system|

GB2203572B|1987-03-24|1991-11-27|Insignia Solutions Limited|Improvements in data processing means|

TW313282U|1991-03-07|1997-08-11|Digital Equipment Corp|Apparatus for automatically interfacing call conventions between two dissimilar program units|

US5390314A|1992-10-09|1995-02-14|American Airlines, Inc.|Method and apparatus for developing scripts that access mainframe resources that can be executed on various computer systems having different interface languages without modification|

IL111154D0|1993-10-21|1994-12-29|Martino Ii John A|Systems and methods for electronic messaging|

US5687376A|1994-12-15|1997-11-11|International Business Machines Corporation|System for monitoring performance of advanced graphics driver including filter modules for passing supported commands associated with function calls and recording task execution time for graphic operation|

US5715459A|1994-12-15|1998-02-03|International Business Machines Corporation|Advanced graphics driver architecture|

US5729748A|1995-04-03|1998-03-17|Microsoft Corporation|Call template builder and method|

US5764974A|1995-08-30|1998-06-09|Unisys Corporation|System with user specified pattern definitions for matching input messages and associated decisions for conditionally responding to the input messages|

US5910180A|1995-11-21|1999-06-08|Diamond Multimedia Systems, Inc.|Context virtualizing device driver architecture|

US5754858A|1996-05-01|1998-05-19|Microsoft Corporation|Customizable application project generation process and system|

DE69728640T2|1997-02-21|2005-04-21|Alcatel Sa|Method for generating a computer program|US6026238A|1997-08-18|2000-02-15|Microsoft Corporatrion|Interface conversion modules based upon generalized templates for multiple platform computer systems|

US20010039564A1|1997-10-20|2001-11-08|Victor Hahn|Log on personal computer|

US6330006B1|1998-05-12|2001-12-11|Silverstream Software, Inc.|Method and apparatus for synchronizing an application's interface and data|

US6480952B2|1998-05-26|2002-11-12|Advanced Micro Devices, Inc.|Emulation coprocessor|

US6192512B1|1998-09-24|2001-02-20|International Business Machines Corporation|Interpreter with virtualized interface|

US6598169B1|1999-07-26|2003-07-22|Microsoft Corporation|System and method for accessing information made available by a kernel mode driver|

US6772106B1|1999-08-20|2004-08-03|Hewlett-Packard Development Company, L.P.|Retargetable computer design system|

US6442752B1|1999-08-26|2002-08-27|Unisys Corporation|Method, apparatus, and computer program product for replacing a dynamic link libraryof a first computing environment with a dll of a second computing environment that can be invoked from the first computing environment in a transparent manner|

US6745385B1|1999-09-01|2004-06-01|Microsoft Corporation|Fixing incompatible applications by providing stubs for APIs|

US6853868B1|1999-10-15|2005-02-08|Sun Microsystems, Inc.|Cross-platform audio feedback for GUI components|

US6587888B1|1999-12-15|2003-07-01|Networks Associates Technology, Inc.|Dynamic software wrapper|

US7043641B1|2000-03-08|2006-05-09|Igt|Encryption in a secure computerized gaming system|

US7203841B2|2001-03-08|2007-04-10|Igt|Encryption in a secure computerized gaming system|

CA2402389A1|2000-03-08|2002-09-19|Shuffle Master, Inc.|Computerized gaming system, method and apparatus|

US6721949B1|2000-03-27|2004-04-13|General Instrument Corporation|Kernel abstraction layer for digital television set-top box firmware|

US6941520B1|2000-05-09|2005-09-06|International Business Machines Corporation|Method, system, and program for using a user interface program to generate a user interface for an application program|

US6769985B1|2000-05-31|2004-08-03|Igt|Gaming device and method for enhancing the issuance or transfer of an award|

US7695363B2|2000-06-23|2010-04-13|Igt|Gaming device having multiple display interfaces|

US7699699B2|2000-06-23|2010-04-20|Igt|Gaming device having multiple selectable display interfaces based on player's wagers|

US6684388B1|2000-08-22|2004-01-27|International Business Machines Corporation|Method for generating platform independent, language specific computer code|

US6960133B1|2000-08-28|2005-11-01|Igt|Slot machine game having a plurality of ways for a user to obtain payouts based on selection of one or more symbols |

US6935955B1|2000-09-07|2005-08-30|Igt|Gaming device with award and deduction proximity-based sound effect feature|

US6968541B1|2000-10-04|2005-11-22|International Business Machines Corporation|Apparatus and method for template instantiation with a cross compiler|

US6739973B1|2000-10-11|2004-05-25|Igt|Gaming device having changed or generated player stimuli|

US7574346B2|2000-10-30|2009-08-11|Microsoft Corporation|Kernel emulator for non-native program modules|

US20020138821A1|2001-01-23|2002-09-26|Vadim Furman|Method and apparatus for seamless porting of object code between operating system environments|

WO2002061577A2|2001-01-29|2002-08-08|Celoxica Limited|Application program interface for programmable architecture cores|

US20030033588A1|2001-01-29|2003-02-13|John Alexander|System, method and article of manufacture for using a library map to create and maintain IP cores effectively|

WO2002073501A1|2001-03-08|2002-09-19|Shuffle Master, Inc.|Computerized gaming system, method and apparatus|

US7988559B2|2001-03-08|2011-08-02|Igt|Computerized gaming system, method and apparatus|

US6749502B2|2001-03-21|2004-06-15|Igt|Gaming device having a multi-characteristic matching game|

US7640153B2|2001-06-04|2009-12-29|Hewlett-Packard Development Company, L.P.|Networked client-server architecture for transparently transforming and executing applications|

US7016963B1|2001-06-29|2006-03-21|Glow Designs, Llc|Content management and transformation system for digital content|

GB0120611D0|2001-08-24|2001-10-17|Igt Uk Ltd|Video display systems|

US7618317B2|2001-09-10|2009-11-17|Jackson Mark D|Method for developing gaming programs compatible with a computerized gaming operating system and apparatus|

US7931533B2|2001-09-28|2011-04-26|Igt|Game development architecture that decouples the game logic from the graphics logics|

US6902481B2|2001-09-28|2005-06-07|Igt|Decoupling of the graphical presentation of a game from the presentation logic|

US7901291B2|2001-09-28|2011-03-08|Igt|Gaming device operable with platform independent code and method|

US8708828B2|2001-09-28|2014-04-29|Igt|Pluggable modular gaming modifiers and configuration templates for gaming environments|

US7708642B2|2001-10-15|2010-05-04|Igt|Gaming device having pitch-shifted sound and music|

US7666098B2|2001-10-15|2010-02-23|Igt|Gaming device having modified reel spin sounds to highlight and enhance positive player outcomes|

US6848996B2|2001-10-15|2005-02-01|Igt|Gaming device with sound recording changes associated with player inputs|

US7107584B2|2001-10-23|2006-09-12|Microsoft Corporation|Data alignment between native and non-native shared data structures|

EP1463569A4|2001-11-26|2010-06-02|Igt Reno Nev|Pass-through live validation device and method|

US6763423B2|2001-11-30|2004-07-13|International Business Machines Corporation|Storage area network methods and apparatus for logical-to-physical block address mapping|

US7284240B1|2002-02-14|2007-10-16|Microsoft Corporation|API schema language and transformation techniques|

CA2382195A1|2002-04-17|2003-10-17|Ibm Canada Limited-Ibm Canada Limitee|Support for wild card characters in code assistance|

US20030203755A1|2002-04-25|2003-10-30|Shuffle Master, Inc.|Encryption in a secure computerized gaming system|

US7210132B2|2002-05-30|2007-04-24|Microsoft Corporation|Interoperability of objects between various platforms|

CA2391717A1|2002-06-26|2003-12-26|Ibm Canada Limited-Ibm Canada Limitee|Transferring data and storing metadata across a network|

US7058933B2|2002-09-11|2006-06-06|Sun Microsystems, Inc.|Extending custom application development environment modules to a second application development environment|

US7194737B2|2002-10-02|2007-03-20|Infinity Systems Software, Inc.|System and method for expediting and automating mainframe computer setup|

GB0307805D0|2003-04-04|2003-05-07|Intuwave Ltd|A method of enabling source code to be used to generate a first and a second software application,each compatible with a different operating system|

US7254816B2|2003-05-05|2007-08-07|Microsoft Corporation|Device driver conversion and creation|

GB0316531D0|2003-07-15|2003-08-20|Transitive Ltd|Method and apparatus for performing native binding|

US7207038B2|2003-08-29|2007-04-17|Nokia Corporation|Constructing control flows graphs of binary executable programs at post-link time|

US7789748B2|2003-09-04|2010-09-07|Igt|Gaming device having player-selectable music|

US7105736B2|2003-09-09|2006-09-12|Igt|Gaming device having a system for dynamically aligning background music with play session events|

CA2539465C|2003-09-17|2012-12-04|Research In Motion Limited|System and method for management of mutating applications|

US7487493B1|2003-12-30|2009-02-03|Itt Manufacturing Enterprises, Inc.|Method and apparatus for developing standard architecture compliant software for programmable radios|

US7694315B2|2004-02-13|2010-04-06|Microsoft Corporation|Schema-based machine generated programming models|

US7860894B2|2004-05-12|2010-12-28|Oracle International Corporation|Template driven type and mode conversion|

US7370318B1|2004-09-02|2008-05-06|Borland Software Corporation|System and methodology for asynchronous code refactoring with symbol injection|

US7356808B2|2004-09-23|2008-04-08|International Business Machines Corporation|Method, system and program product for porting code utilizing a portable execution environment|

US8043155B2|2004-10-18|2011-10-25|Igt|Gaming device having a plurality of wildcard symbol patterns|

US8364565B2|2004-12-01|2013-01-29|Sap Ag|Systems and methods for data processing|

EP1669919A1|2004-12-01|2006-06-14|Sap Ag|A data processing system and data processing method|

US7653684B2|2004-12-03|2010-01-26|Microsoft Corporation|Enabling inter-subsystem resource sharing|

US20060143222A1|2004-12-23|2006-06-29|Maxime Daniel|Method, program and system for automatic reengineering of a client code|

US7685593B2|2005-05-12|2010-03-23|Microsoft Corporation|Systems and methods for supporting multiple gaming console emulation environments|

US8046777B2|2005-06-02|2011-10-25|The Mathworks, Inc.|Calling of late bound functions from an external program environment|

JP4218766B2|2006-03-09|2009-02-04|インターナショナル・ビジネス・マシーンズ・コーポレーション|Method, apparatus and program for testing scenarios|

US20070220531A1|2006-03-15|2007-09-20|Microsoft Corporation|Method and system for shimming COM objects|

US7886284B2|2006-09-05|2011-02-08|International Business Machines Corporation|Using a backend simulator to test and develop xforms templates before linking the xforms templates to backend data processing systems|

US20080288582A1|2006-09-25|2008-11-20|Sms.Ac|Systems and methods for passing application pods between multiple social network service environments|

US8491392B2|2006-10-24|2013-07-23|Igt|Gaming system and method having promotions based on player selected gaming environment preferences|

KR100876605B1|2007-01-22|2008-12-31|이쓰리넷|Heterogeneous linked program generating device|

US20090259771A1|2008-04-09|2009-10-15|Tanik Haluk K|Identification of memory cards by host|

US8484609B2|2008-07-16|2013-07-09|Apple Inc.|Specification files for call translation and trace|

US8591308B2|2008-09-10|2013-11-26|Igt|Gaming system and method providing indication of notable symbols including audible indication|

JP5482011B2|2009-08-11|2014-04-23|株式会社リコー|Image forming apparatus, program management system, program management method, and program management program|

US8346710B2|2010-01-29|2013-01-01|Google Inc.|Evaluating statistical significance of test statistics using placebo actions|

JP2011198298A|2010-03-23|2011-10-06|Dainippon Printing Co Ltd|Ic card and computer program|

US8943483B2|2010-11-11|2015-01-27|International Business Machines Corporation|Application programming interface naming using collaborative services|

US20120278125A1|2011-04-29|2012-11-01|Verizon Patent And Licensing Inc.|Method and system for assessing process management tools|

US8776094B2|2011-08-11|2014-07-08|Microsoft Corporation|Runtime system|

US8695021B2|2011-08-31|2014-04-08|Microsoft Corporation|Projecting native application programming interfaces of an operating system into other programming languages|

CN103092599A|2011-11-05|2013-05-08|京瓷办公信息系统株式会社|Software develop kit|

US9134969B2|2011-12-13|2015-09-15|Ipar, Llc|Computer-implemented systems and methods for providing consistent application generation|

US8460090B1|2012-01-20|2013-06-11|Igt|Gaming system, gaming device, and method providing an estimated emotional state of a player based on the occurrence of one or more designated events|

US8740689B2|2012-07-06|2014-06-03|Igt|Gaming system and method configured to operate a game associated with a reflector symbol|

US9245407B2|2012-07-06|2016-01-26|Igt|Gaming system and method that determines awards based on quantities of symbols included in one or more strings of related symbols displayed along one or more paylines|

US9141325B2|2013-02-01|2015-09-22|Amadeus S.A.S.|Communications management|

US9192857B2|2013-07-23|2015-11-24|Igt|Beat synchronization in a game|

JP5754524B2|2014-02-19|2015-07-29|株式会社リコー|Apparatus, information processing system, information processing method, and information processing program|

US20150281378A1|2014-03-14|2015-10-01|Avni Networks Inc.|Method and apparatus for automating creation of user interface across multi-clouds|

US9680708B2|2014-03-14|2017-06-13|Veritas Technologies|Method and apparatus for cloud resource delivery|

US10635504B2|2014-10-16|2020-04-28|Microsoft Technology Licensing, Llc|API versioning independent of product releases|

US10007500B1|2015-01-21|2018-06-26|Pivotal Software, Inc.|Cloud computing platform architecture|

US9529630B1|2015-01-21|2016-12-27|Pivotal Software, Inc.|Cloud computing platform architecture|

FR3036206B1|2015-05-11|2017-06-09|Thales Sa|METHOD FOR REUSING CERTIFIED MEANS FOR IMPLEMENTING A FUNCTION EMBARKED IN PARTICULAR ABOARD AN AIRCRAFT|

US9986040B2|2015-07-21|2018-05-29|Amadeus S.A.S.|Communications management system with a separate peripherals server|

US9947170B2|2015-09-28|2018-04-17|Igt|Time synchronization of gaming machines|

KR101696101B1|2015-10-21|2017-01-13|주식회사 포스코|Task server and middleware server of steel process middleware service development system|

US10650046B2|2016-02-05|2020-05-12|Sas Institute Inc.|Many task computing with distributed file system|

US10642896B2|2016-02-05|2020-05-05|Sas Institute Inc.|Handling of data sets during execution of task routines of multiple languages|

US10795935B2|2016-02-05|2020-10-06|Sas Institute Inc.|Automated generation of job flow definitions|

US10503498B2|2017-11-16|2019-12-10|Sas Institute Inc.|Scalable cloud-based time series analysis|

法律状态:
2008-04-11| FPAY| Fee payment|Year of fee payment: 4 |

2012-04-11| FPAY| Fee payment|Year of fee payment: 8 |

2014-12-09| AS| Assignment|Owner name: MICROSOFT TECHNOLOGY LICENSING, LLC, WASHINGTON Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:MICROSOFT CORPORATION;REEL/FRAME:034541/0001 Effective date: 20141014 |

2016-06-03| REMI| Maintenance fee reminder mailed|

2016-10-26| LAPS| Lapse for failure to pay maintenance fees|

2016-11-21| STCH| Information on status: patent discontinuation|Free format text: PATENT EXPIRED DUE TO NONPAYMENT OF MAINTENANCE FEES UNDER 37 CFR 1.362 |

2016-12-13| FP| Lapsed due to failure to pay maintenance fee|Effective date: 20161026 |

优先权:

申请号 | 申请日 | 专利标题

US08/912,454|US6026238A|1997-08-18|1997-08-18|Interface conversion modules based upon generalized templates for multiple platform computer systems|

US09/461,860|US6233731B1|1997-08-18|1999-12-15|Program-interface converter for multiple-platform computer systems|

US09/791,006|US6810517B2|1997-08-18|2001-02-22|Program-interface converter for multiple-platform computer systems|US09/791,006| US6810517B2|1997-08-18|2001-02-22|Program-interface converter for multiple-platform computer systems|

[返回顶部]